Fix Java 17 compilation issue by upgrading Lombok and Maven compiler plugin#194
Closed
Fix Java 17 compilation issue by upgrading Lombok and Maven compiler plugin#194
Conversation
…plugin Co-authored-by: lorenzogm <2147574+lorenzogm@users.noreply.github.com>
Co-authored-by: lorenzogm <2147574+lorenzogm@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] test issue
Fix Java 17 compilation issue by upgrading Lombok and Maven compiler plugin
Jul 11, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR resolves a critical compilation issue that was preventing the project from building on Java 17 environments.
Problem
The project was encountering a Java compiler internal error when building:
This error was caused by an incompatibility between:
The issue manifested during annotation processing when Lombok generated code containing switch statements that triggered a bug in the Java 17 compiler.
Solution
release=8instead ofsource/target=1.8Verification
CompilationTestto verify Lombok annotations and enum usage work correctlyImpact
This fix enables developers to build the project on modern Java environments while maintaining Java 8 bytecode compatibility for AEM deployment.
Fixes #193.
Warning
Firewall rules blocked me from connecting to one or more addresses
I tried to connect to the following addresses, but was blocked by firewall rules:
repo.adobe.com/usr/lib/jvm/temurin-17-jdk-amd64/bin/java --enable-native-access=ALL-UNNAMED -classpath /usr/share/apache-maven-3.9.10/boot/plexus-classworlds-2.9.0.jar -Dclassworlds.conf=/usr/share/apache-maven-3.9.10/bin/m2.conf -Dmaven.home=/usr/share/apache-maven-3.9.10 -Dlibrary.jansi.path=/usr/share/apache-maven-3.9.10/lib/jansi-native -Dmaven.multiModuleProjectDirectory=/home/REDACTED/work/saas-aem-module/saas-aem-module org.codehaus.plexus.classworlds.launcher.Launcher clean compile -q(dns block)/usr/lib/jvm/temurin-17-jdk-amd64/bin/java --enable-native-access=ALL-UNNAMED -classpath /usr/share/apache-maven-3.9.10/boot/plexus-classworlds-2.9.0.jar -Dclassworlds.conf=/usr/share/apache-maven-3.9.10/bin/m2.conf -Dmaven.home=/usr/share/apache-maven-3.9.10 -Dlibrary.jansi.path=/usr/share/apache-maven-3.9.10/lib/jansi-native -Dmaven.multiModuleProjectDirectory=/home/REDACTED/work/saas-aem-module/saas-aem-module/api org.codehaus.plexus.classworlds.launcher.Launcher clean test -q(dns block)/usr/lib/jvm/temurin-17-jdk-amd64/bin/java --enable-native-access=ALL-UNNAMED -classpath /usr/share/apache-maven-3.9.10/boot/plexus-classworlds-2.9.0.jar -Dclassworlds.conf=/usr/share/apache-maven-3.9.10/bin/m2.conf -Dmaven.home=/usr/share/apache-maven-3.9.10 -Dlibrary.jansi.path=/usr/share/apache-maven-3.9.10/lib/jansi-native -Dmaven.multiModuleProjectDirectory=/home/REDACTED/work/saas-aem-module/saas-aem-module/core org.codehaus.plexus.classworlds.launcher.Launcher clean compile -q -f core/pom.xml(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.